Use a subquery instead of a join for the assignment user filter #6582
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
For:
In general a subquery is better for filtering, in this case because:
It allows us to compose a query better, we don't have to worry about missing/duplicating a join
It can be faster for non-correlated subqueries (ie queries that produce the same values for all rows). This should be the case here.
They don't introduce duplicate rows, we can remove the distinct here.
No behaviour changes, to sanity check:
Launch the dashboard and list assignments in the dropdown and for one particular course.
Use the student drop down to filter assignments.